projects / gpsbabel.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8fd790e) | patch
The lezyne "super gps", every 10th ride or so, outputs a .fit file
authorTim Connors <tconnors@rather.puzzling.org>
Sat, 14 Sep 2019 12:06:06 +0000 (22:06 +1000)
committerTim Connors <tconnors@rather.puzzling.org>
Sat, 14 Sep 2019 12:06:06 +0000 (22:06 +1000)
commit9210ebce9cf52d446ea8fb60dcf49b2c9530c640
tree6aa392684c23bf27d7079dd01cfbdcea54319596tree | snapshot
parent8fd790e1beceaee4062b4694f0b699c12c5cfafecommit | diff
The lezyne "super gps", every 10th ride or so, outputs a .fit file
that is entirely valid other than a weird non 0/1 endian field.  Don't
dump the data just because of that.
garmin_fit.cc diff | blob | history
reference/track/lezyne_super_gps-garmin_fit-sample-bad-endian.fit [new file with mode: 0755] blob
reference/track/lezyne_super_gps-garmin_fit-sample-bad-endian.gpx [new file with mode: 0644] blob
testo.d/garmin_fit.test diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.